home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 21
/
Cream of the Crop 21 (Terry Blount) (October 1996).iso
/
bbs
/
pad311.zip
/
PADLOCK.DOC
< prev
next >
Wrap
Text File
|
1996-09-02
|
20KB
|
470 lines
P A D L O C K
-------------------------------------------------
version 3.10
(C) 1996 Stefan Xenos
L e g a l S t u f f
_____________________
This software is entirely without warrantly, expressed or implied.
If you decide to use it, you do so at your own risk. The only thing I
guarantee about it is that it will take up space on your hard disk. I take
no responsibility for anything that happens through your use of this
software, no matter how bad it is.
If people weren't in the habit of suing everyone who looked at them
the wrong way, then time and space-wasting messages like this would be
unnecessary.
You may modify this source code however you like for your own
personal use as long as the copyright message and the author's name is not
removed. You MAY NOT distribute modified versions of the code. You may not
charge money for the use or distribution of this program without my prior
permission in writing. Feel free to distribute it like crazy as long as you
don't charge for it.
You may:
- Use Padlock on any sort of electronic bulletin board system,
even those that charge money for access or provide some
commercial service.
- Distribute Padlock on a BBS or through the internet. In fact,
I'd encourage you to distribute this software like there was
no tomorrow.
- Modify the source code for your own personal use.
- Use portions of Padlock's source code for writing other utilities,
as long as you don't distribute them without my prior permission
in writing.
You may do the following only with my prior permission in writing:
- Charge money for the use or distribution of Padlock.
- Distribute Padlock on CD-ROM or diskette as part of a compilation
of other shareware and freeware.
- Include Padlock in the distribution of some other product.
- Use any part of Padlock's source code in another piece of software
available publicly.
You may not:
- Take credit for writing Padlock or any portion thereof, no matter
how much you've modified its source code.
- Distribute modified versions of Padlock.
- Add or remove any files to the Padlock distribution archive. This
includes BBS adds.
- Remove the copyright notice or author's name from the program.
- Reproduce the source code in any form.
Please remember that this is copyrighted software. Although it is
free, it is NOT in the public domain. If you've written bug fixes
or patches for Padlock, please do not distribute them. Instead,
send them to me for inclusion in the next release, and if I decide
to include them, you will be credited for your work.
I n t r o d u c t i o n
_______________________
The document you are reading now was put together in a real rush.
I'm hoping to include better documetation in a future release. If there's
any die-hard Padlock user out there who would be interested in writing a
better user's manual for me, I'd be very grateful. <grin>
Padlock is a flexible call back verifier for Maximus 3.xx and up.
It has been written entirely in Mex (The Maximus EXtension Language) to
ensure portability and to enable you to customize it however you want.
Pleez exkuze my speling. I havint had a chanse to spel chek this
fiel yet.
F e a t u r e s
_______________
This section describes Padlock's features and describes its behaviour.
If you just want to get started
Padlock's features include:
- Multinode friendly.
- International phone number support.
- Padlock can often guess a user's phone number if it is in the
wrong format.
- Sysop-definable logic for adding prefixes and suffixes to phone
numbers from particular areas.
- Verifications to different areas can be restricted to particular
times of the day.
- The user's city can be updated based on their phone number.
- Auto detection of long distance phone numbers.
- Baudrate checking.
- Many wildcards are supported for specifying phone numbers in the
input file.
- Additional verification attempts can be made if another user tries
to call the BBS during a verification.
- Runs under DOS, Win 95, OS/2 2.1, and OS/2 Warp.
- Most output is done through user-editable .MEC files.
- Complete Mex source code included.
- The user's security level can be automatically updated after
a successful verification. User keys can also be added or removed.
- Cursor animation and line editing for most user input.
- Very flexible. Every aspect of Padlock's behaviour is user
configurable. Padlock can even be set up to duplicate the behaviour
of most other popular verifiers.
S y s t e m R e q u i r e m e n t s
_____________________________________
In order to run Padlock, you must have the following:
- Maximus CBCS v3.00 or higher. Padlock will NOT run with Maximus
versions earlier than version 3, and it will not run with any
other BBS package (sorry).
- An operating system capable of running Maximus 3.00. Padlock
should be able to run under any environment Maximus can.
- 500k of hard disk space.
I have tested Padlock 3.00 using the default settings on a Pentium 90
with a USR Sportster 14.4k under DOS 6.22, OS/2 2.1, OS/2 Warp, and
Win 95. In addition, OS/2 2.1 and OS/2 Warp were tested with a
Zoom 28.8k modem.
I n s t a l l a t i o n
_______________________
1. Move all the files into their own directory. By default, I use a
directory inside my main Max directory called PADLOCK.
2. Back up all the default control files that come with Padlock
just in case you change something that doesn't work.
3. Edit SETTINGS.MH. Follow the instructions in that file for more
information.
You may want to further customize Padlock by editing the file
INSETUP.MH, which controls the behaviour of the input/output
routines.
4. If you are upgrading from version 1.5, you will be able to use
your old PHONE.CTL file. Just rename the default PHONE.CTL that
comes with Padlock and copy yours into the padlock directory.
Otherwise, edit the file PHONE.CTL to reflect your local calling
area. Follow the instructions in that file for more information.
5. Edit PADLOCK.MEC. The last five lines should look like:
[MEX]padlock\init
[MEX]padlock\getphone
[MEX]padlock\checknum
[MEX]padlock\verify
Change these lines to reflect the directory that the padlock
mex files are kept in. For example, if you're keeping padlock
in the directory c:\stuff, change these lines to read:
[MEX]stuff\init
[MEX]stuff\getphone
[MEX]stuff\checknum
[MEX]stuff\verify
If you are keeping Padlock in the default directory (a directory
called "padlock" inside your main Max directory), then you
won't need to modify PADLOCK.MEC.
5. Go into the padlock directory and type
BUILD [maximus directory] [mex include directory]
where [maximus directory] is the directory where the maximus
executables can be found and [mex include directory] is the
dire